I’ve recently being getting deeper into the weeds (so to speak) with Power Automate. Whilst this product clearly isn’t a fully fledged programming model, it does sit very nicely in that “low code” methodology, and can be extremely effective when there is a need to quickly create and perform a specific task.

➡️

Firstly, let me register that I much prefer writing raw SQL when interrogating iSAMS than using the official iSAMS REST API - there, I’ve said it!

However, I do entirely appreciate the necessity for an official API in order to cater for security, consistency, potential database schema changes & futureproofing etc. As such, the need to embrace the iSAMS API is I feel, something of a requirement.

➡️

Like many people, I’ve tinkered with Power BI over the years but have never really dug deep into the weeds; the same can also be said for the iSAMS REST API. So recently I thought why not combine these two systems and see what can be achieved?

➡️

It’s been eight months since my last blog post, having taken on a new job, been on the receiving end of a full-on enterprise ransomware attack (that wasn’t nice!) and quite frankly experiencing one heck of a baptism of fire - I felt it was time do write a quick blog post tip!

➡️

During the summer of 2014, we migrated the St Mary’s Shaftesbury MIS (Management Information System) from Schoolbase to iSAMS.

Please note, that the reasons for instigating this major system change, and the processes involved (political & technical), are not covered in this blog post.

➡️